home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Grand Slam 3
/
Grand Slam 3.iso
/
003
/
sigkit.arj
/
SIGPOL4.ARJ
/
SIGPOL4.000
Wrap
Text File
|
1992-04-04
|
33KB
|
846 lines
SIGnet Policy Document
Proposed Version 4.0
2nd April 1992
1. PURPOSE AND POLICY OVERVIEW . . . . . . . . . . . . . . . 1
1.1 General Behaviour. . . . . . . . . . . . . . . . . . 1
1.2 Official Language. . . . . . . . . . . . . . . . . . 1
2. STRUCTURE OF SIGNET . . . . . . . . . . . . . . . . . . . 2
2.1 Basic Topology . . . . . . . . . . . . . . . . . . . 2
2.1.1 Splitting Zones. . . . . . . . . . . . . . 2
2.1.2 Splitting Regions. . . . . . . . . . . . . 2
2.1.3 Splitting Nets . . . . . . . . . . . . . . 2
2.2 Zone Allocation. . . . . . . . . . . . . . . . . . . 3
2.3 The SIGnet Domain. . . . . . . . . . . . . . . . . . 3
2.4 Regions. . . . . . . . . . . . . . . . . . . . . . . 3
2.5 Nets . . . . . . . . . . . . . . . . . . . . . . . . 3
2.6 Net Mail Hour (NMH). . . . . . . . . . . . . . . . . 4
3 ADMINISTRATION. . . . . . . . . . . . . . . . . . . . . . 4
3.1 General. . . . . . . . . . . . . . . . . . . . . . . 4
3.2 International Coordinator (IC) . . . . . . . . . . . 4
3.2.1 Extraordinary Powers of the IC . . . . . . 5
3.3 Zone Coordinator (ZC). . . . . . . . . . . . . . . . 5
3.3.1 ZC Duties. . . . . . . . . . . . . . . . . 5
3.3.2 Extraordinary Powers of the ZC . . . . . . 6
3.4 Zone Echo Coordinator - ZEC. . . . . . . . . . . . . 6
3.4.1 ZEC Duties . . . . . . . . . . . . . . . . 6
3.5 Zone Technical Coordinator - ZTC . . . . . . . . . . 7
3.5.1 ZTC Duties . . . . . . . . . . . . . . . . 7
3.6 Regional Coordinator - RC. . . . . . . . . . . . . . 7
3.6.1 RC Duties. . . . . . . . . . . . . . . . . 7
3.7 Regional Echo Coordinator - REC. . . . . . . . . . . 8
3.7.1 REC Duties . . . . . . . . . . . . . . . . 8
3.8 Net Coordinator - NC . . . . . . . . . . . . . . . . 8
3.8.1 NC Duties. . . . . . . . . . . . . . . . . 8
3.9 Net Echo Coordinator - NEC . . . . . . . . . . . . . 9
3.9.1 NEC Duties . . . . . . . . . . . . . . . . 9
3.10 Ombudsman. . . . . . . . . . . . . . . . . . . . . . 9
4 DISPUTES & COMPLAINTS . . . . . . . . . . . . . . . . . . 9
5 ELECTIONS & REFERENDUMS . . . . . . . . . . . . . . . . 10
5.1 General. . . . . . . . . . . . . . . . . . . . . . 10
5.2 Terms of Office. . . . . . . . . . . . . . . . . . 10
5.3 Calling an Election. . . . . . . . . . . . . . . . 10
5.4 The Election Process . . . . . . . . . . . . . . . 10
6 THE NODELIST. . . . . . . . . . . . . . . . . . . . . . 11
6.1 General. . . . . . . . . . . . . . . . . . . . . . 11
6.2 Nodelist Structure . . . . . . . . . . . . . . . . 11
6.3 Special Node Numbers . . . . . . . . . . . . . . . 11
6.4 Official Editing and Distribution. . . . . . . . . 11
7 APPLICATION FOR A NODE NUMBER - MEMBERSHIP. . . . . . . 12
7.1 Responsibility of Assignment . . . . . . . . . . . 12
7.2 Availability and Eligibility . . . . . . . . . . . 12
7.3 Exclusion. . . . . . . . . . . . . . . . . . . . . 12
7.3.1 Limitations of Bans. . . . . . . . . . . . . 12
7.4 Limit of Nodes . . . . . . . . . . . . . . . . . . 12
7.5 Private Nodes. . . . . . . . . . . . . . . . . . . 13
8 ECHOMAIL CONFERENCES. . . . . . . . . . . . . . . . . . 13
8.1 Different Types of Echomail. . . . . . . . . . . . 13
8.2 Censorship . . . . . . . . . . . . . . . . . . . . 13
8.3 Cutting off Mail Flow. . . . . . . . . . . . . . . 13
8.5 Sysop's Responsibility . . . . . . . . . . . . . . 14
8.6 Legal Action Due to Conferences. . . . . . . . . . 14
8.7 Personal Opinions and Beliefs. . . . . . . . . . . 15
8.8 Technical Matters. . . . . . . . . . . . . . . . . 15
9 TECHNICAL SPECIFICATIONS. . . . . . . . . . . . . . . . 15
10 ZONE SPECIFIC POLICY. . . . . . . . . . . . . . . . . . 15
11 SPECIAL INTEREST GROUPS . . . . . . . . . . . . . . . . 16
11.1 Membership of SIGnet . . . . . . . . . . . . . . . 16
11.2 Conflict of Interest . . . . . . . . . . . . . . . 16
11.3 Furtherment of SIGnet. . . . . . . . . . . . . . . 16
12 SIGNET POLICY (SIGpol) CHANGES. . . . . . . . . . . . . 17
13 COPYRIGHT AND OWNERSHIP OF SIGNET . . . . . . . . . . . 17
13.1 Copyright Notice . . . . . . . . . . . . . . . . . 17
SIGnet Policy V4.0 as at 2nd April 1992................Page 1
1. PURPOSE AND POLICY OVERVIEW
SIGnet's purpose is to provide an international medium in
which people of different cultures with different interests
can share discussion with other people. SIGnet strives to
provide this in a friendly, open atmosphere which is
obtainable without undue difficulty by any system in the
SIGnet nodelist.
SIGnet also strives to create an umbrella under which unique
special interest groups may have a common medium in which to
communicate both amongst themselves and with other groups
which may have similar or different interests.
SIGnet is a network, open to all sysops operating electronic
bulletin boards, public or private, anywhere in the world that
is capable of the FTSC standard packet and handshake format.
There shall be no exclusion of anyone from joining SIGnet
based on race, sex, creed, religion, age, colour, or
nationality. SIGnet does not exclude any individual based on
their membership in other networks, unless a common
inter-network body, of which SIGnet is a member, has
recommended a ban of the sysop.
1.1 General Behaviour
SIGnet is based on the basic ideals of fairness and
friendship. Public flaming will not be tolerated. If you feel
the need to flame or argue with another individual in the
network, it should be done in private so as not to disrupt the
entire network. Putting down an individual who is not a
member of SIGnet will also not be tolerated.
1.2 Official Language
The official language of SIGnet is and shall remain as
English. Although this document may be freely translated into
other languages, the text, contents and intent of the clauses
contained herein are to be considered correct and proper as
written and interpreted in the official language.
SIGnet Policy V4.0 as at 2nd April 1992................Page 2
2. STRUCTURE OF SIGNET
2.1 Basic Topology
SIGnet consists of a series of Zones based on their
geographical location. These Zones will comprise various
Regions which will consist of several Nets which in turn will
consist of individual nodes. Every member of SIGnet must have
a node number and belong to a Net.
Generally there should be a maximum of 30 Regions per zone. In
each region, there should be a maximum of 30 nets. There
should be a maximum of 30 nodes in a net. Zone Co-Ordinators
should not allow a Region or Net to exceed its ability to
properly execute its purpose.
2.1.1 Splitting Zones
Should the Zone Coordinator and the International Coordinator
(in concert) feel that a Zone encompasses too much area to run
properly or that for any reason the zone should be split into
more than one area, the IC (International Coordinator) may
split the zone and allocate a new zone number to the new zone.
2.1.2 Splitting Regions
Should the Region Coordinator and the Zone Coordinator (in
concert) feel that a Region encompasses too much area to run
properly or that for any reason the Region should be split
into more than one area, the Zone Coordinator may split the
Region and allocate a new Region number to the new Region.
2.1.3 Splitting Nets
Should the Net Coordinator and the Region Coordinator (in
concert) feel that a Net encompasses too much area to run
properly or that for any reason the Net should be split into
more than one area, the Region Coordinator may split the Net
and allocate a new Net number to the new Net.
SIGnet Policy V4.0 as at 2nd April 1992................Page 3
2.2 Zone Allocation
The following zones have been allocated for use in SIGnet:
Zone 24 SIGnet Administration
Zone 25 Western Canada and Alaska
Zone 26 Continental United States
Zone 27 Europe
Zone 28 Australia, New Zealand and South Pacific
Zone 29 Asia
Zone 30 Africa
Zone 31 South America
Zone 32 Central Asia
Zone 33 Western Asia and Middle East
Zone 34 Eastern Canada
2.3 The SIGnet Domain
SIGnet currently operates and recognises only one domain
signature. Domain usage should only contain @signet as the
domain signature. At this time, any additional characters in
the domain signature will be ignored.
2.4 Regions
Regions are allocated by the Zone Coordinator. It is entirely
up to the ZC to devise a unique scheme of numbering Regions.
It is recommended that the telephone/postal area code, country
code or some other generally well known numbers in the Zone
should be used.
2.5 Nets
Nets are allocated by the Region Coordinator. Generally, more
than one net should not cover the same area that another net
covers. This may not be feasible should the density of a
particular area be so great that a single net would simply not
cover it effectively.
SIGnet Policy V4.0 as at 2nd April 1992................Page 4
2.6 Net Mail Hour (NMH)
All systems are required to be able to receive or pickup mail
during this time.
NMH is established and advised by your Zone Coordinator.
3 ADMINISTRATION
3.1 General
SIGnet will be administered on each level by an elected
individual. These will consist of the International, Zone,
Region and Net levels. The International Coordinator shall
oversee the entire operation of SIGnet and maintain the
direction and intent of the network.
3.2 International Coordinator (IC)
The IC will be elected by a simple majority of the Zone
Coordinators to hold the position for a period of not longer
than 12 months. He may seek re-election and there is no
maximum number of terms for which he can hold the position.
The IC can be replaced at any time by a simple majority vote
of no-confidence by the ZC's.
The IC can also hold the position of a Zone Coordinator in
which case, in addition to his vote being counted as a Zone
Coordinator he will also hold a casting vote in his position
as IC.
The IC shall oversee all administration objectives of the
network including new policy development, consultation with
all levels of administration in policy interpretation, network
structure, and dispute and appeal mediation.
In addition, it is the IC's duty to promote SIGnet in good
faith to other networks, sysops and future sysops, and the
general public in any way that he sees fit.
SIGnet Policy V4.0 as at 2nd April 1992................Page 5
It shall also be the duty of the IC to ensure the distribution
of the SIGnet nodelist once per week as outlined in this
document.
The IC may, from time to time, appoint members of SIGnet to
special committees to develop policy and technical
specification.
3.2.1 Extraordinary Powers of the IC
From time to time the IC may need to remove or otherwise
replace and appoint any Coordinator in SIGnet to ensure SIGpol
and the aims of SIGnet are not compromised. Should the IC so
act, he is required to seek confirmation of his actions from
a simple majority of the Zone Coordinators within seven days
of so acting. This authority covers the entire extent of
SIGnet including Zones, Regions and Nets however it is
anticipated the IC would only act after consultation with the
appropriate Coordinator.
3.3 Zone Coordinator (ZC)
The ZC will be elected by a simple majority of the Regional
Coordinators in that Zone to hold the position for a period of
not longer than 12 months. He may seek re-election and there
is no maximum number of terms for which he can hold the
position.
The ZC can be replaced at any time by a simple majority vote
of no-confidence by the RC's in that Zone.
3.3.1 ZC Duties
The ZC shall:
(i) compile nodelist updates for submission to the IC for
compilation;
(ii) distribute the following files to the RH's in their zone
for distribution:
- SIGDIFF.*
- SNEWS???.*
- SIGECHO.*
(iii) assign new regions in their zone as needed in accordance
with this policy;
SIGnet Policy V4.0 as at 2nd April 1992................Page 6
(iv) maintain the smooth flow and operation of their zone in
SIGnet;
(v) work with the ZEC to assure smooth flow of echomail in
their zone;
(vi) act as an inter-zone netmail hub for the members in their
zone.
3.3.2 Extraordinary Powers of the ZC
From time to time the ZC may need to remove or otherwise
replace and appoint any Coordinator in their Zone to ensure
SIGpol and the aims of SIGnet are not compromised. Should the
ZC so act, he is required to seek confirmation of his actions
from a simple majority of the Regional Coordinators within
seven days of so acting. This authority covers the entire
extent of the SIGnet Zone including Regions and Nets however
it is anticipated the ZC would only act after consultation
with the appropriate Coordinator.
3.4 Zone Echo Coordinator - ZEC
Each Zone Coordinator in SIGnet, must appoint a Zone Echo
Coordinator (ZEC). In the case of the administration zone, the
IC shall appoint an International Echo Coordinator (IEC).
3.4.1 ZEC Duties
The ZEC shall:
(i) distribute all mandatory echos to all downlinks in their
zone;
(ii) shall make readily available to all downlinks all echos
originating in SIGnet as well as echomail gated between zones;
(iii) make available to any system in their zone, a list of
all echomail conferences available to the systems in their
zone.
The ZC may also perform the duties of the ZEC. In this case,
the ZC shall maintain both nodelist entries.
SIGnet Policy V4.0 as at 2nd April 1992................Page 7
3.5 Zone Technical Coordinator - ZTC
Each zone in SIGnet should appoint a Zone Technical
Coordinator.
3.5.1 ZTC Duties
The ZTC shall be a backup system to the ZC and ZEC in the
event that either party is unable to perform their function
until such time that the problem can be rectified or an
election take place. The ZTC will also act as a technical
adviser to the ZC and ZEC at their request.
3.6 Regional Coordinator - RC
The RC will be elected by a simple majority of the Net
Coordinators in that Region to hold the position for a period
of not longer than 12 months. He may seek re-election and
there is no maximum number of terms for which he can hold the
position.
The RC can be replaced at any time by a simple majority vote
of no-confidence by the NC's in that Region.
3.6.1 RC Duties
The RC shall:
(i) compile nodelist updates for submission to the ZC for
compilation;
(ii) distribute the following files to the Nets in their
region for distribution:
- SIGDIFF.*
- SNEWS???.*
- SIGECHO.*
(iii) assign new nets in their region as needed in compliance
with this policy;
(iv) maintain the smooth flow and operation of their region in
SIGnet;
(v) work with the REC to assure smooth flow of echomail in
their region.
SIGnet Policy V4.0 as at 2nd April 1992................Page 8
3.7 Regional Echo Coordinator - REC
Each Region in SIGnet must appoint a Regional Echo Coordinator
(REC).
3.7.1 REC Duties
The REC shall:
(i) distribute all mandatory echos to all downlinks in their
region;
(ii) shall make available to all downlinks all echos available
in their zone;
(iii) make available to any system in their region, a list of
all echomail conferences available to the systems in their
zone.
The RC may also perform the duties of the REC. In this case,
the RC shall maintain both nodelist entries.
3.8 Net Coordinator - NC
The NC will be elected by a simple majority of the Nodes in
the Net to hold the position for a period of not longer than
12 months. He may seek re-election and there is no maximum
number of terms for which he can hold the position.
The NC can be replaced at any time by a simple majority vote
of no-confidence by the nodes in the net.
3.8.1 NC Duties
The NC shall:
(i) compile nodelist updates for submission to the RC for
compilation;
(ii) distribute the following files to the nodes in their net;
- SIGDIFF.*
- SNEWS???.*
- SIGECHO.*
(iii) assign new node numbers in their net as needed in
compliance with this policy;
SIGnet Policy V4.0 as at 2nd April 1992................Page 9
(iv) maintain the smooth flow and operation of their net in
SIGnet;
(v) work with the NEC to assure smooth flow of echomail in
their net.
3.9 Net Echo Coordinator - NEC
Each net in SIGnet must appoint a Net Echo Coordinator (NEC).
3.9.1 NEC Duties
The NEC shall:
(i) distribute all mandatory echos to all nodes in their net;
(ii) shall make available to all nodes all echos available in
their zone;
(iii) make available to any system in their net, a list of all
echomail conferences available to the systems in their zone.
The NC may also perform the duties of the NEC. In this case,
the NC shall maintain both nodelist entries.
3.10 Ombudsman
Any level of administration in SIGnet may choose to put forth
an election for an Ombudsman to handle disputes at their
level. Should the administration choose not to elect the
Ombudsman, the IC, ZC, RC or NC shall assume responsibility
for handling disputes.
4 DISPUTES & COMPLAINTS
From time to time nodes will have cause to either dispute or
complain about another node within SIGnet. Full operational
details on how to go about lodging such dispute or complaint
can be found in the SIGops manual however the following Policy
matters prevail:-
(a) The complaint or dispute must be lodged with the next
level of administration involved in the dispute.
(b) A copy of the complaint or dispute must be netmailed to
each party in the dispute.
SIGnet Policy V4.0 as at 2nd April 1992................Page 10
(c) The IC, ZC, RC, NC or Ombudsman (depending on the level
to which the dispute has been addressed is to adjudicate
in as speedily fashion as considered prudent.
(d) Either party in the dispute may lodge an appeal to the
next level above the Coordinator at (c) above however the
person appealed to will have the final decision.
5 ELECTIONS & REFERENDUMS
5.1 General
As outlined in Section 3, all levels of administration in
SIGnet are performed by members of the network elected into
their position by a simple majority vote of members in their
electorate. It is believed that by using this process, the
people will be more fairly represented in policy discussions
and the general direction of the network by people whom they
have elected to represent them.
5.2 Terms of Office
No elected person shall remain in office longer than 12 months
without seeking re-election. Persons appointed to positions by
a Coordinator are also subject to the same length of term.
5.3 Calling an Election
An election will be called by the present encumbent (or any
other Coordinator in superiority) within a reasonable time
frame to allow for the orderly conduct of an election.
5.4 The Election Process
The election process and procedures are fully set out in the
SIGops manual.
SIGnet Policy V4.0 as at 2nd April 1992................Page 11
6 THE NODELIST
6.1 General
SIGnet's nodelist shall be know as the SIGnodes whilst the
update file shall be known as the SIGdiff.
The SIGnet nodelist update (SIGdiff) shall be distributed
weekly by the ZC's, to the RC's, to the NC's and finally to
the individual nodes.
The up-to-date nodelist (SIGnodes) shall also be available for
file request from the ZC's, RC's and NC's.
6.2 Nodelist Structure
The flags and general structure of the nodelist shall conform
to current FTSC standards which presently call for a St. Louis
style nodelist.
6.3 Special Node Numbers
Certain administration positions shall require uniformity
throughout the nodelist. They shall be as follows:
*C xxx:yyy/0.0
*EC xxx:yyy/1.0
ZTC xxx:xxx/2.0
Ombudsman xxx:yyy/3.0
No other node segment under 10 shall be issued without prior
consent from the ZC. Numbers 4 through 9 shall be reserved for
future use at all levels of SIGnet.
6.4 Official Editing and Distribution
No person, other than the respective ZC (or the IC), shall
edit or distribute the official release copy or any other copy
for release of the SIGnet nodelist or nodelist update file.
SIGnet Policy V4.0 as at 2nd April 1992................Page 12
7 APPLICATION FOR A NODE NUMBER - MEMBERSHIP
7.1 Responsibility of Assignment
SIGnet node numbers are given out in local nets by the NC. It
is the job of the NC to determine that an accepted node has
received a copy of this Policy document, and that the node
understands and agrees to abide by the policies laid out
herein.
Where there is a Zone Policy in place, the new node must
understand and abide by the local policies laid out therein.
7.2 Availability and Eligibility
In order for a system to obtain a SIGnet node number, their
request for the node number must be made via netmail. Private
email and echomail shall not be sufficient proof that the
system is mail capable. In addition, the potential node must
be able to receive or pickup mail during NMH.
7.3 Exclusion
No individual shall be excluded from joining SIGnet for any
reason whatsoever except in the event of an international ban
based on proven behaviour in other networks.
7.3.1 Limitations of Bans
Should an individual be banned from SIGnet or any other
network, they shall only be banned from SIGnet for a period
not exceeding 3 years. They may reapply for a node number in
SIGnet every 6 months when the ban will be reconsidered by the
RC in concert with the NC.
7.4 Limit of Nodes
No system shall retain a node number in more than one net.
SIGnet Policy V4.0 as at 2nd April 1992................Page 13
7.5 Private Nodes
SIGnet supports and encourages the use of the PVT flag in the
nodelist for private nodes and points. The use of points is
discouraged (but allowed). Setting up a PVT node is a far
better alternative as it allows the proper distribution of
information between people. A PVT node shall have the same
rights and be under the same regulations as a standard entry
as is outlined in this document.
8 ECHOMAIL CONFERENCES
8.1 Different Types of Echomail
For general usage, there shall be only two distinct types of
echomail in SIGnet.
(i) SIGnet Originating - this shall be a conference which is
available only within SIGnet or a conference which originates
within SIGnet and may be gated out to other networks.
(ii) Imported - this shall be a conference which originates
outside of SIGnet and is gated into the network properly and
legally.
8.2 Censorship
The use of automated or manual censorship tools in SIGnet is
expressly forbidden. The use of such tools will be grounds
under the terms of this document for expulsion from SIGnet.
8.3 Cutting off Mail Flow
No node shall be permitted to control the flow of any echomail
conference or routed netmail for any reason whatsoever without
the express written permission of the appropriate
International, Zone or Regional Coordinator. Any system making
any threat or performing any action which results in any
number of systems being without mail without just cause may be
expelled from SIGnet.
SIGnet Policy V4.0 as at 2nd April 1992................Page 14
8.4 Imported Echos
All conferences being gated into SIGnet from other networks
shall be moderated by the moderators from the foreign network
and SIGnet nodes shall conform fully to the requirements of
the conference moderator.
Any node repeatedly not conforming to the rules of an imported
conference may have its feed of the conference terminated
without warning. If you are unsure about the rules, ask the
moderator.
8.5 Sysop's Responsibility
Sysops of nodes are solely responsible for mail entered on
their system and are expected to take action generally
regarded as appropriate assuming the message entered by a
given individual does not meet generally accepted standards.
Further, the sysop of the system on which the message was
entered shall make a full report to the net as to what has
been done to eliminate the situation.
8.6 Legal Action Due to Conferences
Any conference which may be cause for legal action against
SIGnet, any host passing the conference, or any system in
SIGnet carrying the conference shall be deemed to be in
contradiction of the policy, attitude and general concept of
SIGnet. The conference in question will be indefinitely
suspended from SIGnet circulation until it can be determined
whether there is violation of civil or corporate law. This
action should not be viewed as censorship. It is not the
personal opinion of any sysop, host, or system in the network
which causes this action but the governing laws and
legislation of the geographic area involved.
SIGnet Policy V4.0 as at 2nd April 1992................Page 15
8.7 Personal Opinions and Beliefs
No host in SIGnet shall let his or her personal opinions or
beliefs prevent them from allowing access to echomail of any
type to any system.
It is not the purpose of a host to judge or predetermine what
is right or what is wrong. In the event that a host is unable
or unwilling to carry a public conference in SIGnet due to
personal beliefs or reasons, that host should either provide
immediate alternative sources to his or her downlinks or
resign the position.
8.8 Technical Matters
Further details pertaining to technical matters regarding
echomail conferences are fully detailed in the SIGops Manual.
9 TECHNICAL SPECIFICATIONS
Operational and technical matters pertaining to SIGnet are
fully covered in the SIGnet Operations Manual - SIGops.
The SIGops Manual is kept up to date by the ZC's and may be
freely amended from time to time by the ZC's.
10 ZONE SPECIFIC POLICY
Due to varying circumstances between Zones, Zones are
encouraged to establish and maintain their own Zone Policy.
These policies can cover items that relate to their own zone
eg cost-sharing arrangements.
Zone Policies can be established/amended by a simple majority
vote of the electorate.
Zone Policies do not affect any node outside of that Zone and
should there be any difference in interpretation between
SIGpol and Zone Policy, SIGpol will take precedence.
SIGnet Policy V4.0 as at 2nd April 1992................Page 16
11 SPECIAL INTEREST GROUPS
Special Interest Group's (SIG's) are encouraged to use the
SIGnet mail backbone for their use as this is one of the
primary purposes of SIGnet.
11.1 Membership of SIGnet
Each member of a SIG wishing to utilise the SIGnet echomail or
file facilities is required to become a node in SIGnet and
comply with all the Policies of SIGnet including Zone Policy.
Providing the SIG member also allows access to the facilities
of SIGnet to members of the public outside of the SIG
membership, that SIG member can also hold any Co-Ordinator
position within SIGnet if he/she is so elected.
11.2 Conflict of Interest
SIG's will need to comply with and agree to abide by all the
policies and principals as set forth from time to time in the
SIGnet and Zone Policy documents. Any SIG found to be in
breach of those principals and/or policies may be subject to
expulsion from SIGnet although normal rights of appeal or
dispute settlement procedures detailed in SIGnet Policy will
apply.
11.3 Furtherment of SIGnet
SIG members are encouraged to foster SIGnet and make available
to the users of their BBS systems, SIGnet message echo's and
facilities not necessarily related to their SIG although this
is not compulsory.
SIG members are required to receive all the compulsory echo's
as detailed in SIGnet and Zone Policy documents. They are
strongly encouraged to participate in these echo's and be
alert for information regarding mail flow, elections etc.
SIGnet Policy V4.0 as at 2nd April 1992................Page 17
12 SIGNET POLICY (SIGpol) CHANGES
Proposed amendments to this policy document can be made by
submission to your Zone Coordinator either by netmail or via
an appropriate Sysops Only echo.
The Zone Coordinator should encourage general discussion and
should a positive consensus emerge then the proposed amendment
should be raised with all the other Zone Coordinators for
discussion by all SIGnet nodes.
Should a simple majority of the Zone Coordinators consider a
formal change to policy is worthy of a full plebiscite then
such should be arranged in a timely fashion.
Any changes to SIGnet Policy will require a full plebiscite of
all nodes and will come into full force and effect by a simple
majority of the nodes voting in favour of the amendment.
13 COPYRIGHT AND OWNERSHIP OF SIGNET
13.1 Copyright Notice
SIGnet, SIGnews, SIGdiff, SIGnodes and the SIGnet Policy
Document are all trademarks and are Copyright (C) 1991, 1992
by SIGnet and its members.
All rights are reserved worldwide and no use of the copyright
trademarks may be used without the prior written consent of
the owner. This copyright in no way controls the contents of
the nodelist but only the names SIGnodes and SIGdiff.